Sourced from org.jetbrains.kotlinx.binary-compatibility-validator's releases.

0.16.3

What's Changed:

• Fixed support for Gradle version older than 8.2 (#263)

0.16.2

What's Changed:

• The plugin was changed to use the Gradle Workers API and its classpath isolation mode to remove almost all dependencies from the plugin itself; all required libraries are now fetched on demand, in isolation from the buildscript classpath (#208, #256, #258).

0.16.0

What changed:

• Updated Kotlin Metadata JVM library to the latest version (now it's kotlin-metadata-jvm:2.0.0) #255
• Various improvements in KLib ABI dumping API #253, #254

0.15.1

What changed:

• Fixed a regression introduced in 0.15.0 affecting how enum entries from classes with non-public companions are dumped (#250)

0.15.0

This release finalizes what was added in the series of beta releases and adds Kotlin libraries (KLib) dumping and validation support. See project's README for details on how to enable it for your project.

The release contains some breaking changes that were made to align and fix BCV behavior across all supported configurations:

• BCV now (again) uses case-sensitive dump file names (Kotlin/binary-compatibility-validator#237);
• Multiplatform projects having no release sources (for instance, test-only projects) now need to be either explicitly excluded or an empty dump file needs to be generated for them (Kotlin/binary-compatibility-validator#231);
• Gradle tasks provided by the plugin changed their API to use Gradle Properties instead of plain Kotlin properties.

If any of these changes affect your projects, please check the migration guide for details on what needs to be done to update BCV to 0.15.0: 0.15.0 Migration Guide.

What changed:

From 0.15.0-Beta.3

• Non-public markers are now correctly handled when applied to const vals (#90, #245)
• Fixed KLib dump and validation behavior for empty projects (#246, #247); now apiDump will emit an empty file and apiCheck will successfully consume it

From 0.14.0 (brief overview of Beta.1 .. Beta.3 changes)

• List<ClassBinarySignature>.dump now sorts declarations the same way the Gradle task does (Kotlin/binary-compatibility-validator#188)
• API dump file names (for both JVM and Klib dumps) need to be case-sensitive (Kotlin/binary-compatibility-validator#231, Kotlin/binary-compatibility-validator#237)
• Validation behavior for empty projects was aligned across all supported configurations (Kotlin/binary-compatibility-validator#243, Kotlin/binary-compatibility-validator#244); now, such projects must either contain API dump files or be explicitly excluded using ignoredProjects.
• Experimental KLib ABI dumping and validation support was added (#183, #203, #196, #197, #234, #219, #214)

I want to give a shout-out to everyone involved! Special thanks to @​benedekh, @​adam-enko, @​JakeWharton, @​rickclephas, @​lukellmann, @​illarionov, @​sandwwraith, @​martinbonnin, @​ilya-g and @​shanshin for their feedback and contributions.

0.15.0-Beta.3

This release provides updated KLib validation support and fixes some previously reported KLib-related issues.

The release contains some breaking changes that were made to align and fix BCV behavior across all supported configurations:

• BCV now (again) uses case-sensitive dump file names (#237);
• Multiplatform projects having no release sources (for instance, test-only projects) now need to be either explicitly excluded or an empty dump file needs to be generated for them (#231);
• Gradle tasks provided by the plugin changed their API to use Gradle Properties instead of plain Kotlin properties.

... (truncated)

• 18cd0df Release 0.16.3
• 65282d1 Fixed support for Gradle < 7.0 (#267)
• c00ca4b Fixed support for Gradle < 8.2 (#265)
• 14ebd02 Upgrade version
• 1305a6a Removed configuration time check for plugin version (#258)
• f1e2076 Introduced usage of worker API
• 05c1eca Version 0.16.0
• 6428c88 Update kotlin-metadata-jvm (#255)
• 040922e Fix KlibDumpFilters factory name (#254)
• daebfc1 KlibDump API imporovements (#253)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)